Non-Segregated Network

The non-segregated network is represented would look like

In this case, all of the 4 networks would map to VM Network / Management Network. Users would still need to provide details for each of the networks separately. Users can divide the IP subnet into multiple ranges which can be mapped to these four networks.

For example, for a network 10.102.0.0/16, we can have following IP ranges and can be used accordingly:

• 10.102.1.2 - 10.102.1.20 (VM Network)
• 10.102.1.21 - 10.102.1.40 (ESXi_Network)
• 10.102.1.41 - 10.102.1.60 (Uplink_WAN_Network)
• 10.102.1.61 - 10.102.1.80 (HDM_Internal_Networking)

During HDM deployment, users are required to categorize and map the networks discovered in the vCenter as per the types mentioned above.

In this case all of the “Source Networks” would map to VM Network / Management Network during the deployment process as shown below.

Network planning spreadsheet

Please download the spreadsheet Planning Template and use along with your deployment process.

The Planning Template is an active spreadsheet which will allow you to specify the deployment mode you have chosen. You need to select the correct mode using the drop down.

1. Choose the "Cloud Type"
2. Choose the "Deployment Mode"
3. Choose the "Resource Allocation"

After this you need to fill in the number of ESXi on-premises and on the cloud. For VMware Cloud Director the number of nodes on the cloud is irrelevant and please fill in 1 here.

The rest of the form requires you to fill in network configuration details like IP address, ranges. The dynamic part of the form gives you information on the number of the resources you need to provision.

The information in the Planning Template is almost identical to the sections below and should serve to identify the size of the IP pool required and capture information for easy entry during the deployment steps.

HDM Network Configuration - Planning

Please fill the table below for use during installation later.

Network requirements during on-premises deployment

During the premises deployment phase of the installation we will configure the following networks on-premises.

1. HDM_Internal_Network
2. Uplink_WAN_Network
3. ESXi_Network

These are the same as the ones described in previous section on OVF Deployment. During the premises deployment however you need to provide a range or list of IPs for each of these networks.

For all the 3 categories of network, choose the IP allocation mechanism : static IP.

For static IP, following details are required for configuration.

• IP range : IP list that are free to be allocated for use.
• Subnet mask : subnet of the IP range
• Gateway : gateway IP of the network
• Domain : domain name of the network
• DNS : to translate the domain name to IP
• NTP : for time sync

A pool of IP addresses need to be allocated. The number of IPs for each category are

HDM_Internal_Network: 2 IPs required

Uplink_WAN_Network: 2 IPs required

ESXi_Network: 2 IPs required

Note:

1. The subnet range 172.17.0.0/16 is not available for the deployment; it is internally used by HDM microservices.
2. Please check the static ip usage using arping command before using it to ensure that ip should not be in use. arping -c 2 -w 20 -I ens192 [IP]

HDM_Internal_Network

Uplink_WAN_Network

ESXi_Network

Network requirement during on-cloud deployment

Similar to the previous two deployment stages we need to provision IPs and identify the correct networks that satisfy the connectivity requirements. The networks that need to be configured are.

HDM Internal network: 20 IP pool. Will also be used for VMs during migration

WAN network configuration: 2 IPs.

Please fill the table below for reference during the installation process.

HDM_Internal_Network

Uplink_WAN_Network

WAN Routing Configuration

The following WAN routes are required to access on-cloud from on-premises and vice-versa. This is required in during the Set WAN route part of cloud configuration.

• On-premises WAN network details

  The route which would be set on HDM appliance on-premises. The routes will enable communication from on-premises to HDM appliances on-cloud.

  • On-Premises WAN subnet : Subnet of premises WAN network on which HDM appliances are deployed
  • On-Premises WAN gateway : On-premises WAN gateway which allows access to on-cloud WAN subnet

• On-cloud WAN network details

  The route which would be set on HDM components on the cloud. The routes will enable communication from the cloud components to HDM appliances on-premises.

  • On-cloud WAN subnet : Subnet of cloud WAN network on which HDM appliances are deployed
  • On-cloud WAN gateway : On-cloud WAN gateway which allows access to on-premises WAN subnet